@jeremypw I feel like this should be two separate branches, one that should be merged immediately to add release notes for the things that have already been merged. This way we get plenty of time for translators to work. And a second release labeled branch with the wishlist for things to merge before releasing. Otherwise if we're waiting before everything is merged before adding release notes, we're not giving translators any time

@danirabbit I'll probably drop from this release any PRs that are not merged within the next day or two and then finalize the metadata. I will then leave a week or so for translation. Hopefully that is sufficient.

@jeremypw Any PRs you want me to take a look at today to try and get in for the release?

@jeremypw Any PRs you want me to take a look at today to try and get in for the release?

Thanks for the offer - I noticed it after dropping the unreviewed PRs from this release unfortunately. I need to get this PR merged soon so that translation can be done by the release target date so will not be merging anymore non-critical stuff before the next release (I'm not aware of anything critical atm). However, another release will be made next month

@zeebok. The release data will be finalized by the actual release commit. I seem to remember having an issue with setting future dates in the metadata.

I am also trying to get a Files release out soon and elementary/files#2616 needs testing if you are interested.